Skip to content

Update daily environment to use 8.7 SNAPSHOT#758

Merged
ofiriro3 merged 126 commits into
elastic:mainfrom
ofiriro3:weekly-enviroment-vanilla-work-with-SNAPSHOT
Feb 26, 2023
Merged

Update daily environment to use 8.7 SNAPSHOT#758
ofiriro3 merged 126 commits into
elastic:mainfrom
ofiriro3:weekly-enviroment-vanilla-work-with-SNAPSHOT

Conversation

@ofiriro3

@ofiriro3 ofiriro3 commented Feb 20, 2023

Copy link
Copy Markdown
Contributor

Prerequisite

  • Before merging this change we need to replace the secret.API_KEY with a relevant stagging API_KEY.

Summary of your changes

We would like to update the daily environment to use the 8.7 SNAPSHOT while using the stagging cloud environment.

In-depth
As developers, we would like that the daily environment to represent the current content in the main branch.
That way, we would be able to detect bugs earlier in the development process, bugs that may appear only after a few fetching cycles.

** Currently 8.8 SNAPSHOT is broken, so this PR will deploy 8.7 SNAPSHOT.
I created another ticket to replace the hard-coded version with the latest SNAPSHOT.

How to test
Currently, the flow is deployed using a dispatch workflow, meaning - you will need to apply it using GitHub actions.
You can apply the flow from my fork, using actions.
Please set the branch to weekly-enviroment-vanilla-work-with-SNAPSHOT before running the dispatch workflow.
image

A new environment should be created with the 8.7 SNAPSHOT version.
You will receive the credentials to a dedicated slack channel named ofir-personal-channel.

Expected behavior

  • A new 8.7 SNAPSHOT will be created with the vanilla benchmark installed.
  • The cloud environment should be deployed on staging.found.no
  • A slack message with the relevant credentials should be sent to ofir-personal-channel.
  • You should get findings for the relevant benchmark.

Related Issues

Depends On

@mergify

mergify Bot commented Feb 20, 2023

Copy link
Copy Markdown
Contributor

This pull request does not have a backport label. Could you fix it @ofiriro3? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit
    NOTE: backport-skip has been added to this pull request.

@github-actions

Copy link
Copy Markdown

@mergify

mergify Bot commented Feb 23, 2023

Copy link
Copy Markdown
Contributor

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b weekly-enviroment-vanilla-work-with-SNAPSHOT upstream/weekly-enviroment-vanilla-work-with-SNAPSHOT
git merge upstream/main
git push upstream weekly-enviroment-vanilla-work-with-SNAPSHOT

@ofiriro3
ofiriro3 marked this pull request as ready for review February 23, 2023 14:24
@ofiriro3
ofiriro3 requested review from a team as code owners February 23, 2023 14:24
@ofiriro3
ofiriro3 requested a review from oren-zohar February 23, 2023 14:24
"title": "Kubernetes Security Posture Management (KSPM)",
"version": "1.1.1"
"title": "Security Posture Management (CSPM/KSPM)",
"version": "1.2.10"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this version is not stable, no?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I know the broken integration is 1.2.11, but the integration will auto-upgrade to 1.2.11 after the deployment.
As far as I saw I got findings as usual, although the agent wasn't healthy (on 1.2.11).

Do you think it would be better to deploy @jeniawhite version? 1.2.12-next

Comment thread deploy/weekly-environment/variables.tf

@oren-zohar oren-zohar left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As developers, we would like that the daily environment to represent the current content in the main branch.

Main is 8.8, and if this is the idea, why not dynamically use the version from the branch?

@ofiriro3 ofiriro3 left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commented 🙏

Comment thread deploy/weekly-environment/variables.tf
"title": "Kubernetes Security Posture Management (KSPM)",
"version": "1.1.1"
"title": "Security Posture Management (CSPM/KSPM)",
"version": "1.2.10"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I know the broken integration is 1.2.11, but the integration will auto-upgrade to 1.2.11 after the deployment.
As far as I saw I got findings as usual, although the agent wasn't healthy (on 1.2.11).

Do you think it would be better to deploy @jeniawhite version? 1.2.12-next

@ofiriro3
ofiriro3 requested a review from oren-zohar February 23, 2023 14:56
@ofiriro3

Copy link
Copy Markdown
Contributor Author

Main is 8.8, and if this is the idea, why not dynamically use the version from the branch?

Yes that is a valid option.
Currently 8.8-SNAPSHOT is broken, so we put the 8.7-SNAPSHOT instead.

I'll update the description here.

This is a reference to an item I already created before:

@ofiriro3
ofiriro3 merged commit f7246e6 into elastic:main Feb 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants